home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Development Foundation 1.1 for IRIX 6.4
/
SGI IRIX 6.4 Development Foundation 1.1.iso
/
relnotes
/
patchSG0002909
/
ch1.z
/
ch1
Wrap
Text File
|
1998-03-26
|
5KB
|
199 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_2_9_0_9__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0002909 WorkShop cvd
slow on startup on n32 C/C++ applications for WorkShop
2.6.5.
Patch SG0002909 replaces patch SG0002639-WorkShop: cvd
rollup patch for WorkShop 2.6.5, patch SG0002407-WorkShop:
cvd exception traps stop on wrong exceptions for Ada95, and
patch SG0002587-WorkShop: cvd cannot set breakpoint in C++
code.
1.1 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch is to WorkShop 2.6.5 cvd and will install on any
system on which WorkShop 2.6.5 is installed.
1.2 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_2_9_0_9
This patch contains fixes for the following bugs in WorkShop
2.6.5:
+o WorkShop cvd rollup patch: cvd slow on startup on n32
C/C++ applications (Bug #540624)
+o WorkShop: cvd exception traps stop on wrong exceptions
for Ada95 (bug #515232)
+o WorkShop: cvd cannot set breakpoint in C++ code (bug
#507377)
+o WorkShop: pcs core dump while profiling Ada application
(bug #540850)
1.3 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_2_9_0_9
This patch release includes these subsystems:
+o patchSG0002909.WorkShop_sw.cvd
1.4 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.2), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 of these release notes, you
are unsure whether your software meet the requirements for
- 2 -
installing a particular patch, run _i_n_s_t. The _i_n_s_t program
does not allow you to install patches that are incompatible
with your hardware or software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _S_o_f_t_w_a_r_e
_I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
4. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
1.5 _P_a_t_c_h__R_e_m_o_v_a_l__I_n_s_t_r_u_c_t_i_o_n_s
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
- 3 -
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
Ocassionally the call stack view shows <stripped> instead of
the function name.
Performance experiemnts on IRIS GL programs will sometimes
give incorrect results when call stack samples originate in
the GL libraries. The assembly routines for some functions
do not have the proper directives to allow SpeedShop to
correctly unwind the stack through some GL routines,
therefore user routines that call these GL routines will not
show up in the stack trace, and possibly not in the function
list and call graph if said user routines do not have hits
of their own.